<!DOCTYPE html> 


<html lang="en">
  <head>
    <meta charset="utf-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <title>
  
    RFC 6222 - Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)
  
</title>
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <style>

  @media only screen 
    and (min-width: 992px)
    and (max-width: 1199px) {
      body { font-size: 14pt; }
            div.content { width: 96ex; margin: 0 auto; }
        }
  @media only screen 
    and (min-width: 768px)
    and (max-width: 991px) {
            body { font-size: 14pt; }
            div.content { width: 96ex; margin: 0 auto; }
        }
  @media only screen 
    and (min-width: 480px)
    and (max-width: 767px) {
            body { font-size: 11pt; }
            div.content { width: 96ex; margin: 0 auto; }
        }
  @media only screen 
    and (max-width: 479px) {
            body { font-size: 8pt; }
            div.content { width: 96ex; margin: 0 auto; }
        }
  @media only screen 
    and (min-device-width : 375px) 
    and (max-device-width : 667px) {
            body { font-size: 9.5pt; }
            div.content { width: 96ex; margin: 0; }
        }
  @media only screen 
    and (min-device-width: 1200px) {
            body { font-size: 10pt; margin: 0 4em; }
            div.content { width: 96ex; margin: 0; }
        }
        h1, h2, h3, h4, h5, h6, .h1, .h2, .h3, .h4, .h5, .h6 {
      font-weight: bold;
            /* line-height: 0pt; */
            display: inline;
            white-space: pre;
            font-family: monospace;
            font-size: 1em;
      font-weight: bold;
        }
        pre {
            font-size: 1em;
            margin-top: 0px;
            margin-bottom: 0px;
        }
  .pre {
      white-space: pre;
      font-family: monospace;
  }
  .header{
      font-weight: bold;
  }
        .newpage {
            page-break-before: always;
        }
        .invisible {
            text-decoration: none;
            color: white;
        }
        @media print {
            body {
                margin-top: 5em;
                font-family: monospace;
                font-size: 10.5pt;
            }
            h1, h2, h3, h4, h5, h6 {
                font-size: 1em;
            }
        
            a:link, a:visited {
                color: inherit;
                text-decoration: none;
            }
            .noprint {
                display: none;
            }
        }
  @media screen {
      .grey, .grey a:link, .grey a:visited {
    color: #777;
      }
            .meta-info {
                background-color: #EEE;
            }
            .top {
                border-top: 7px solid #EEE;
            }
            .pad {
                padding-top: 7px;
                line-height: 24px;
                padding-bottom: 4px;
            }
            .bgwhite  { background-color: white; }
            .bgred    { background-color: #F44; }
            .bggrey   { background-color: #666; }
            .bgbrown  { background-color: #840; }            
            .bgorange { background-color: #FA0; }
            .bgyellow { background-color: #EE0; }
            .bgmagenta{ background-color: #F4F; }
            .bgblue   { background-color: #66F; }
            .bgcyan   { background-color: #4DD; }
            .bggreen  { background-color: #4F4; }

            .legend   { font-size: 90%; }
            .cplate   { font-size: 70%; border: solid grey 1px; }
  }
    
     

.bgwhite  { background-color: white; }
.bgred    { background-color: #F44; }
.bggrey   { background-color: #666; }
.bgbrown  { background-color: #840; }            
.bgorange { background-color: #FA0; }
.bgyellow { background-color: #EE0; }
.bgmagenta{ background-color: #F4F; }
.bgblue   { background-color: #66F; }
.bgcyan   { background-color: #4DD; }
.bggreen  { background-color: #4F4; }

.draftcontent { margin-top:0px !important;}


    </style>

    
  <link rel="alternate" type="application/atom+xml" title="Document changes" href="/feed/document-changes/draft-ietf-avt-rtp-cnames/">
  <meta name="description" content="Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs) (RFC )">


    
    <link rel="shortcut icon" href="https://www.ietf.org/lib/dt/7.46.0/ietf/images/ietf-icon-blue3.png">
    
    <link rel="apple-touch-icon" href="https://www.ietf.org/lib/dt/7.46.0/ietf/images/apple-touch-icon.png">
  </head>

  <body style="padding-top: 0;">

	  <div class="content" id="content">
        
  
 
  <div class="rfcmarkup">
    <div class="noprint" style="height: 6px;">
      <div onmouseover="this.style.cursor='pointer';"
         onclick="showLegend();"
         onmouseout="hideLegend()"
         style="height: 6px; min-height: 6px; width: 96ex; position: absolute; margin-top:0; "
         class="meta-info bgbrown"
         title="Click for colour legend." >&nbsp;</div>
      <div id="legend"
           class="meta-info noprint pre legend"
           style="position:absolute; top: 4px; left: 4ex; visibility:hidden; background-color: white; padding: 4px 9px 5px 7px; border: solid #345 1px; "
           onmouseover="showLegend();"
           onmouseout="hideLegend();">
      </div>
    </div>

    
      <div class="noprint">
	 <pre class="pre meta-info">[<a href="https://datatracker.ietf.org" title="Document search and retrieval page">Search</a>] [<a href="https://www.rfc-editor.org/rfc/rfc6222.txt" title="Plaintext version of this document">txt</a>|<a href="https://www.rfc-editor.org/rfc/rfc6222.html" title="HTML version of this document, from XML2RFC">html</a>|<a href="https://www.rfc-editor.org/rfc/pdfrfc/rfc6222.txt.pdf" title="PDF version of this document">pdf</a>|<a href="/doc/rfc6222/bibtex/" title="BibTex entry for this document">bibtex</a>] [<a href="/doc/rfc6222/" title="Datatracker information for this document">Tracker</a>] [<a href="/group/avt/" title="The working group handling this document">WG</a>] [<a href="mailto:draft-ietf-avt-rtp-cnames@ietf.org?subject=draft-ietf-avt-rtp-cnames" title="Send email to the document authors">Email</a>] [<a href="https://www.ietf.org/rfcdiff?difftype=--hwdiff&url2=draft-ietf-avt-rtp-cnames-05.txt" title="Inline diff (wdiff)">Diff1</a>] [<a href="https://www.ietf.org/rfcdiff?url2=draft-ietf-avt-rtp-cnames-05.txt" title="Side-by-side diff">Diff2</a>] [<a href="https://www.ietf.org/tools/idnits?url=https://www.ietf.org/archive/id/draft-ietf-avt-rtp-cnames-05.txt" title="Run an idnits check of this document">Nits</a>]

From: <a href="/doc/html/draft-ietf-avt-rtp-cnames-05">draft-ietf-avt-rtp-cnames-05</a>                     Proposed Standard
Obsoleted by: <a href="/doc/html/rfc7022">7022</a>                                                      </pre>
      </div>
    

    <div class="draftcontent">
    <pre>Internet Engineering Task Force (IETF)                          A. Begen
Request for Comments: 6222                                         Cisco
Updates: <a href="/doc/html/rfc3550">3550</a>                                                 C. Perkins
Category: Standards Track                          University of Glasgow
ISSN: 2070-1721                                                  D. Wing
                                                                   Cisco
                                                              April 2011


          <span class="h1">Guidelines for Choosing RTP Control Protocol (RTCP)</span>
                        <span class="h1">Canonical Names (CNAMEs)</span>

Abstract

   The RTP Control Protocol (RTCP) Canonical Name (CNAME) is a
   persistent transport-level identifier for an RTP endpoint.  While the
   Synchronization Source (SSRC) identifier of an RTP endpoint may
   change if a collision is detected or when the RTP application is
   restarted, its RTCP CNAME is meant to stay unchanged, so that RTP
   endpoints can be uniquely identified and associated with their RTP
   media streams.  For proper functionality, RTCP CNAMEs should be
   unique within the participants of an RTP session.  However, the
   existing guidelines for choosing the RTCP CNAME provided in the RTP
   standard are insufficient to achieve this uniqueness.  This memo
   updates those guidelines to allow endpoints to choose unique RTCP
   CNAMEs.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in <a href="/doc/html/rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   <a href="https://www.rfc-editor.org/info/rfc6222">http://www.rfc-editor.org/info/rfc6222</a>.











<span class="grey">Begen, et al.                Standards Track                    [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="/doc/html/rfc6222">RFC 6222</a>                 Choosing an RTCP CNAME               April 2011</span>


Copyright Notice

   Copyright (c) 2011 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to <a href="/doc/html/bcp78">BCP 78</a> and the IETF Trust&#x27;s Legal
   Provisions Relating to IETF Documents
   (<a href="https://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
   <a href="#section-2">2</a>. Requirements Notation ...........................................<a href="#page-2">2</a>
   3. Deficiencies with Earlier Guidelines for Choosing an
      RTCP CNAME ......................................................<a href="#page-3">3</a>
   <a href="#section-4">4</a>. Choosing an RTCP CNAME ..........................................<a href="#page-3">3</a>
      <a href="#section-4.1">4.1</a>. Persistent RTCP CNAMEs versus Per-Session RTCP CNAMEs ......<a href="#page-4">4</a>
      <a href="#section-4.2">4.2</a>. Requirements ...............................................<a href="#page-5">5</a>
   <a href="#section-5">5</a>. Procedure to Generate a Unique Identifier .......................<a href="#page-6">6</a>
   <a href="#section-6">6</a>. Security Considerations .........................................<a href="#page-7">7</a>
      <a href="#section-6.1">6.1</a>. Considerations on Uniqueness of RTCP CNAMEs ................<a href="#page-7">7</a>
      <a href="#section-6.2">6.2</a>. Session Correlation Based on RTCP CNAMEs ...................<a href="#page-7">7</a>
   <a href="#section-7">7</a>. Acknowledgments .................................................<a href="#page-8">8</a>
   <a href="#section-8">8</a>. References ......................................................<a href="#page-8">8</a>
      <a href="#section-8.1">8.1</a>. Normative References .......................................<a href="#page-8">8</a>
      <a href="#section-8.2">8.2</a>. Informative References .....................................<a href="#page-9">9</a>

<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   In <a href="#section-6.5.1">Section 6.5.1</a> of the RTP specification, [<a href="/doc/html/rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>], there are a
   number of recommendations for choosing a unique RTCP CNAME for an RTP
   endpoint.  However, in practice, some of these methods are not
   guaranteed to produce a unique RTCP CNAME.  This memo updates
   guidelines for choosing RTCP CNAMEs, superseding those presented in
   <a href="/doc/html/rfc3550#section-6.5.1">Section&nbsp;6.5.1 of [RFC3550]</a>.

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Requirements Notation</span>

   The key words &quot;MUST&quot;, &quot;MUST NOT&quot;, &quot;REQUIRED&quot;, &quot;SHALL&quot;, &quot;SHALL NOT&quot;,
   &quot;SHOULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMENDED&quot;, &quot;NOT RECOMMENDED&quot;, &quot;MAY&quot;, and
   &quot;OPTIONAL&quot; in this document are to be interpreted as described in
   [<a href="/doc/html/rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].



<span class="grey">Begen, et al.                Standards Track                    [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="/doc/html/rfc6222">RFC 6222</a>                 Choosing an RTCP CNAME               April 2011</span>


<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  Deficiencies with Earlier Guidelines for Choosing an RTCP CNAME</span>

   The recommendation in [<a href="/doc/html/rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>] is to generate an RTCP CNAME of the
   form &quot;user@host&quot; for multiuser systems, or &quot;host&quot; if the username is
   not available.  The &quot;host&quot; part is specified to be the fully
   qualified domain name (FQDN) of the host from which the real-time
   data originates.  While this guidance was appropriate at the time
   [<a href="/doc/html/rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>] was written, FQDNs are no longer necessarily unique and can
   sometimes be common across several endpoints in large service
   provider networks.  This document replaces the use of FQDN as an RTCP
   CNAME by alternative mechanisms.

   IPv4 addresses are also suggested for use in RTCP CNAMEs in
   [<a href="/doc/html/rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>], where the &quot;host&quot; part of the RTCP CNAME is the numeric
   representation of the IPv4 address of the interface from which the
   RTP data originates.  As noted in [<a href="/doc/html/rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>], the use of private
   network address space [<a href="/doc/html/rfc1918" title="&quot;Address Allocation for Private Internets&quot;">RFC1918</a>] can result in hosts having network
   addresses that are not globally unique.  Additionally, this shared
   use of the same IPv4 address can also occur with public IPv4
   addresses if multiple hosts are assigned the same public IPv4 address
   and connected to a Network Address Translation (NAT) device
   [<a href="/doc/html/rfc3022" title="&quot;Traditional IP Network Address Translator (Traditional NAT)&quot;">RFC3022</a>].  When multiple hosts share the same IPv4 address, whether
   private or public, using the IPv4 address as the RTCP CNAME leads to
   RTCP CNAMEs that are not necessarily unique.

   It is also noted in [<a href="/doc/html/rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>] that if hosts with private addresses
   and no direct IP connectivity to the public Internet have their RTP
   packets forwarded to the public Internet through an RTP-level
   translator, they could end up having non-unique RTCP CNAMEs.  The
   suggestion in [<a href="/doc/html/rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>] is that such applications provide a
   configuration option to allow the user to choose a unique RTCP CNAME;
   this technique puts the burden on the translator to translate RTCP
   CNAMEs from private addresses to public addresses if necessary to
   keep private addresses from being exposed.  Experience has shown that
   this does not work well in practice.

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  Choosing an RTCP CNAME</span>

   It is difficult, and in some cases impossible, for a host to
   determine if there is a NAT between itself and its RTP peer.
   Furthermore, even some public IPv4 addresses can be shared by
   multiple hosts in the Internet.  Using the numeric representation of
   the IPv4 address as the &quot;host&quot; part of the RTCP CNAME is NOT
   RECOMMENDED.







<span class="grey">Begen, et al.                Standards Track                    [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="/doc/html/rfc6222">RFC 6222</a>                 Choosing an RTCP CNAME               April 2011</span>


<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>.  Persistent RTCP CNAMEs versus Per-Session RTCP CNAMEs</span>

   The RTCP CNAME can be either persistent across different RTP sessions
   for an RTP endpoint or unique per session, meaning that an RTP
   endpoint chooses a different RTCP CNAME for each RTP session.

   An RTP endpoint that is emitting multiple related RTP streams that
   require synchronization at the other endpoint(s) MUST use the same
   RTCP CNAME for all streams that are to be synchronized.  This
   requires a short-term persistent RTCP CNAME that is common across
   several RTP streams, and potentially across several related RTP
   sessions.  A common example of such use occurs when lip-syncing audio
   and video streams in a multimedia session, where a single participant
   has to use the same RTCP CNAME for its audio RTP session and for its
   video RTP session.  Another example might be to synchronize the
   layers of a layered audio codec, where the same RTCP CNAME has to be
   used for each layer.

   A longer-term persistent RTCP CNAME is sometimes useful to facilitate
   third-party monitoring, consistent with [<a href="/doc/html/rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>].  One such use
   might be to allow network management tools to correlate the ongoing
   quality of service for a participant across multiple RTP sessions for
   fault diagnosis, and to understand long-term network performance
   statistics.  An implementation that wishes to discourage this type of
   third-party monitoring can generate a unique RTCP CNAME for each RTP
   session, or group of related RTP sessions, that it joins.  Such a
   per-session RTCP CNAME cannot be used for traffic analysis, and so
   provides some limited form of privacy (note that there are non-RTP
   means that can be used by a third party to correlate RTP sessions, so
   the use of per-session RTCP CNAMEs will not prevent a determined
   traffic analyst from monitoring such sessions).

   This memo defines several different ways by which an implementation
   can choose an RTCP CNAME.  It is possible, and legitimate, for
   independent implementations to make different choices of RTCP CNAME
   when running on the same host.  This can hinder third-party
   monitoring, unless some external means is provided to configure a
   persistent choice of RTCP CNAME for those implementations.

   Note that there is no backwards compatibility issue (with [<a href="/doc/html/rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>]-
   compatible implementations) introduced in this memo, since the RTCP
   CNAMEs are opaque strings to remote peers.









<span class="grey">Begen, et al.                Standards Track                    [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="/doc/html/rfc6222">RFC 6222</a>                 Choosing an RTCP CNAME               April 2011</span>


<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>.  Requirements</span>

   RTP endpoints will choose to generate RTCP CNAMEs that are persistent
   or per-session.  An RTP endpoint that wishes to generate a persistent
   RTCP CNAME MUST use one of the following two methods:

   o  To produce a long-term persistent RTCP CNAME, an RTP endpoint MUST
      generate and store a Universally Unique IDentifier (UUID)
      [<a href="/doc/html/rfc4122" title="&quot;A Universally Unique IDentifier (UUID) URN Namespace&quot;">RFC4122</a>] for use as the &quot;host&quot; part of its RTCP CNAME.  The UUID
      MUST be version 1, 2, or 4, as described in [<a href="/doc/html/rfc4122" title="&quot;A Universally Unique IDentifier (UUID) URN Namespace&quot;">RFC4122</a>], with the
      &quot;urn:uuid:&quot; stripped, resulting in a 36-octet printable string
      representation.

   o  To produce a short-term persistent RTCP CNAME, an RTP endpoint
      MUST either (a) use the numeric representation of the layer-2
      (Media Access Control (MAC)) address of the interface that is used
      to initiate the RTP session as the &quot;host&quot; part of its RTCP CNAME
      or (b) generate and use an identifier by following the procedure
      described in <a href="#section-5">Section 5</a>.  In either case, the procedure is
      performed once per initialization of the software.  After
      obtaining an identifier by doing (a) or (b), the least significant
      48 bits are converted to the standard colon-separated hexadecimal
      format [<a href="/doc/html/rfc5342" title="&quot;IANA Considerations and IETF Protocol Usage for IEEE 802 Parameters&quot;">RFC5342</a>], e.g., &quot;00:23:32:af:9b:aa&quot;, resulting in a
      17-octet printable string representation.

   In the two cases above, the &quot;user@&quot; part of the RTCP CNAME MAY be
   omitted on single-user systems and MAY be replaced by an opaque token
   on multi-user systems, to preserve privacy.

   An RTP endpoint that wishes to generate a per-session RTCP CNAME MUST
   use the following method:

   o  For every new RTP session, a new CNAME is generated following the
      procedure described in <a href="#section-5">Section 5</a>.  After performing that
      procedure, the least significant 96 bits are used to generate an
      identifier (to compromise between packet size and security), which
      is converted to ASCII using Base64 encoding [<a href="/doc/html/rfc4648" title="&quot;The Base16, Base32, and Base64 Data Encodings&quot;">RFC4648</a>].  This
      results in a 16-octet string representation.  The RTCP CNAME
      cannot change over the life of an RTP session [<a href="/doc/html/rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>]; hence,
      only the initial SSRC value chosen by the endpoint is used.  The
      &quot;user@&quot; part of the RTCP CNAME is omitted when generating
      per-session RTCP CNAMEs.









<span class="grey">Begen, et al.                Standards Track                    [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="/doc/html/rfc6222">RFC 6222</a>                 Choosing an RTCP CNAME               April 2011</span>


   It is believed that obtaining uniqueness (with a high probability) is
   an important property that requires careful evaluation of the method.
   This document provides a number of methods, at least one of which
   would be suitable for all deployment scenarios.  This document
   therefore does not provide for the implementor to define and select
   an alternative method.

   A future specification might define an alternative method for
   generating RTCP CNAMEs, as long as the proposed method has
   appropriate uniqueness and there is consistency between the methods
   used for multiple RTP sessions that are to be correlated.  However,
   such a specification needs to be reviewed and approved before
   deployment.

   The mechanisms described in this document are to be used to generate
   RTCP CNAMEs, and they are not to be used for generating general-
   purpose unique identifiers.

<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Procedure to Generate a Unique Identifier</span>

   The algorithm described below is intended to be used for locally
   generated unique identifiers.

   1.  Obtain the current time of day in 64-bit NTP format [<a href="/doc/html/rfc5905" title="&quot;Network Time Protocol Version 4: Protocol and Algorithms Specification&quot;">RFC5905</a>].

   2.  Obtain a modified EUI-64 identifier from the system running this
       algorithm [<a href="/doc/html/rfc4291" title="&quot;IP Version 6 Addressing Architecture&quot;">RFC4291</a>].  If such a system does not exist, an
       identifier can be created from a 48-bit MAC address, as specified
       in [<a href="/doc/html/rfc4291" title="&quot;IP Version 6 Addressing Architecture&quot;">RFC4291</a>].  If one cannot be obtained or created, a suitably
       unique identifier, local to the node, should be used (e.g.,
       system serial number).

   3.  Concatenate the time of day with the system-specific identifier
       in order to create a key.

   4.  If generating a per-session CNAME, also concatenate the RTP
       endpoint&#x27;s initial SSRC, the source and destination IP addresses,
       and ports to the key.

   5.  Compute the 256-bit output of the SHA-256 digest of the key, as
       specified in [<a href="/doc/html/rfc4634" title="&quot;US Secure Hash Algorithms (SHA and HMAC-SHA)&quot;">RFC4634</a>].










<span class="grey">Begen, et al.                Standards Track                    [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="/doc/html/rfc6222">RFC 6222</a>                 Choosing an RTCP CNAME               April 2011</span>


<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  Security Considerations</span>

   The security considerations of [<a href="/doc/html/rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>] apply to this memo.

<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>.  Considerations on Uniqueness of RTCP CNAMEs</span>

   The recommendations given in this document for RTCP CNAME generation
   ensure that a set of cooperating participants in an RTP session will,
   with very high probability, have unique RTCP CNAMEs.  However,
   neither [<a href="/doc/html/rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>] nor this document provides any way to ensure that
   participants will choose RTCP CNAMEs appropriately, and thus
   implementations MUST NOT rely on the uniqueness of CNAMEs for any
   essential security services.  This is consistent with [<a href="/doc/html/rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>],
   which does not require that RTCP CNAMEs are unique within a session
   but instead says that condition SHOULD hold.  As described in the
   Security Considerations section of [<a href="/doc/html/rfc3550" title="&quot;RTP: A Transport Protocol for Real-Time Applications&quot;">RFC3550</a>], because each
   participant in a session is free to choose its own RTCP CNAME, they
   can do so in such a way as to impersonate another participant.  That
   is, participants are trusted to not impersonate each other.  No
   recommendation for generating RTCP CNAMEs can prevent this
   impersonation, because an attacker can neglect the stipulation.
   Secure RTP (SRTP) [<a href="/doc/html/rfc3711" title="&quot;The Secure Real-time Transport Protocol (SRTP)&quot;">RFC3711</a>] keeps unauthorized entities out of an RTP
   session, but it does not aim to prevent impersonation attacks from
   unauthorized entities.

   This document uses a hash function to ensure the uniqueness of RTCP
   CNAMEs.  A cryptographic hash function is used because such functions
   provide the randomness properties that are needed.  However, no
   security assumptions are made on the hash function.  The hash
   function is not assumed to be collision resistant, preimage
   resistant, or second preimage resistant in an adversarial setting; as
   described above, an attacker attempting an impersonation attack could
   merely set the RTCP CNAME directly rather than attacking the hash
   function.  Similarly, the hash function is not assumed to be a one-
   way function or pseudorandom in a cryptographic sense.

   No confidentiality is provided on the data used as input to the RTCP
   CNAME generation algorithm.  It might be possible for an attacker who
   observes an RTCP CNAME to determine the inputs that were used to
   generate that value.

<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>.  Session Correlation Based on RTCP CNAMEs</span>

   In some environments, notably telephony, a fixed RTCP CNAME value
   allows separate RTP sessions to be correlated and eliminates the
   obfuscation provided by IPv6 privacy addresses [<a href="/doc/html/rfc4941" title="&quot;Privacy Extensions for Stateless Address Autoconfiguration in IPv6&quot;">RFC4941</a>] or IPv4
   Network Address Port Translation (NAPT) [<a href="/doc/html/rfc3022" title="&quot;Traditional IP Network Address Translator (Traditional NAT)&quot;">RFC3022</a>].  SRTP [<a href="/doc/html/rfc3711" title="&quot;The Secure Real-time Transport Protocol (SRTP)&quot;">RFC3711</a>]
   can help prevent such correlation by encrypting Secure RTCP (SRTCP),



<span class="grey">Begen, et al.                Standards Track                    [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="/doc/html/rfc6222">RFC 6222</a>                 Choosing an RTCP CNAME               April 2011</span>


   but it should be noted that SRTP only mandates SRTCP integrity
   protection (not encryption).  Thus, RTP applications used in such
   environments should consider encrypting their SRTCP or generate a
   per-session RTCP CNAME as discussed in <a href="#section-4.1">Section 4.1</a>.

<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>.  Acknowledgments</span>

   Thanks to Marc Petit-Huguenin, who suggested using UUIDs in
   generating RTCP CNAMEs.  Also, thanks to David McGrew for providing
   text for the Security Considerations section.

<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>.  References</span>

<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>.  Normative References</span>

   [<a id="ref-RFC3550">RFC3550</a>]  Schulzrinne, H., Casner, S., Frederick, R., and V.
              Jacobson, &quot;RTP: A Transport Protocol for Real-Time
              Applications&quot;, STD 64, <a href="/doc/html/rfc3550">RFC 3550</a>, July 2003.

   [<a id="ref-RFC2119">RFC2119</a>]  Bradner, S., &quot;Key words for use in RFCs to Indicate
              Requirement Levels&quot;, <a href="/doc/html/bcp14">BCP 14</a>, <a href="/doc/html/rfc2119">RFC 2119</a>, March 1997.

   [<a id="ref-RFC4122">RFC4122</a>]  Leach, P., Mealling, M., and R. Salz, &quot;A Universally
              Unique IDentifier (UUID) URN Namespace&quot;, <a href="/doc/html/rfc4122">RFC 4122</a>,
              July 2005.

   [<a id="ref-RFC4634">RFC4634</a>]  Eastlake 3rd, D. and T. Hansen, &quot;US Secure Hash Algorithms
              (SHA and HMAC-SHA)&quot;, <a href="/doc/html/rfc4634">RFC 4634</a>, July 2006.

   [<a id="ref-RFC4648">RFC4648</a>]  Josefsson, S., &quot;The Base16, Base32, and Base64 Data
              Encodings&quot;, <a href="/doc/html/rfc4648">RFC 4648</a>, October 2006.

   [<a id="ref-RFC5905">RFC5905</a>]  Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,
              &quot;Network Time Protocol Version 4: Protocol and Algorithms
              Specification&quot;, <a href="/doc/html/rfc5905">RFC 5905</a>, June 2010.

   [<a id="ref-RFC4291">RFC4291</a>]  Hinden, R. and S. Deering, &quot;IP Version 6 Addressing
              Architecture&quot;, <a href="/doc/html/rfc4291">RFC 4291</a>, February 2006.

   [<a id="ref-RFC5342">RFC5342</a>]  Eastlake 3rd, D., &quot;IANA Considerations and IETF Protocol
              Usage for IEEE 802 Parameters&quot;, <a href="/doc/html/bcp141">BCP 141</a>, <a href="/doc/html/rfc5342">RFC 5342</a>,
              September 2008.









<span class="grey">Begen, et al.                Standards Track                    [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="/doc/html/rfc6222">RFC 6222</a>                 Choosing an RTCP CNAME               April 2011</span>


<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>.  Informative References</span>

   [<a id="ref-RFC1918">RFC1918</a>]  Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G.,
              and E. Lear, &quot;Address Allocation for Private Internets&quot;,
              <a href="/doc/html/bcp5">BCP 5</a>, <a href="/doc/html/rfc1918">RFC 1918</a>, February 1996.

   [<a id="ref-RFC3022">RFC3022</a>]  Srisuresh, P. and K. Egevang, &quot;Traditional IP Network
              Address Translator (Traditional NAT)&quot;, <a href="/doc/html/rfc3022">RFC 3022</a>,
              January 2001.

   [<a id="ref-RFC3711">RFC3711</a>]  Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K.
              Norrman, &quot;The Secure Real-time Transport Protocol (SRTP)&quot;,
              <a href="/doc/html/rfc3711">RFC 3711</a>, March 2004.

   [<a id="ref-RFC4941">RFC4941</a>]  Narten, T., Draves, R., and S. Krishnan, &quot;Privacy
              Extensions for Stateless Address Autoconfiguration in
              IPv6&quot;, <a href="/doc/html/rfc4941">RFC 4941</a>, September 2007.

Authors&#x27; Addresses

   Ali Begen
   Cisco
   181 Bay Street
   Toronto, ON  M5J 2T3
   CANADA

   EMail:  abegen@cisco.com


   Colin Perkins
   University of Glasgow
   School of Computing Science
   Glasgow  G12 8QQ
   UK

   EMail:  csp@csperkins.org


   Dan Wing
   Cisco Systems, Inc.
   170 West Tasman Dr.
   San Jose, CA  95134
   USA

   EMail:  dwing@cisco.com






Begen, et al.                Standards Track                    [Page 9]
</pre>
    </div>

  </div>


        
	  </div>

	

	

    </div>

      
    <script type="text/javascript"><!--
    var legend_html = "Colour legend:<br /> \
     <table> \
        <tr><td>Unknown:</td>                   <td><span class='cplate bgwhite'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> \
        <tr><td>Draft:</td>                     <td><span class='cplate bgred'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> \
        <tr><td>Informational:</td>             <td><span class='cplate bgorange'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> \
        <tr><td>Experimental:</td>              <td><span class='cplate bgyellow'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> \
        <tr><td>Best Common Practice:</td>      <td><span class='cplate bgmagenta'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> \
        <tr><td>Proposed Standard:</td>         <td><span class='cplate bgblue'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> \
        <tr><td>Draft Standard (old designation):</td> <td><span class='cplate bgcyan'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> \
        <tr><td>Internet Standard:</td>         <td><span class='cplate bggreen'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> \
        <tr><td>Historic:</td>                  <td><span class='cplate bggrey'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> \
        <tr><td>Obsolete:</td>                  <td><span class='cplate bgbrown'>&nbsp;&nbsp;&nbsp;&nbsp;</span></td></tr> \
    </table>";
    function showLegend() {
        var elem = document.getElementById('legend');
        elem.innerHTML = legend_html
        elem.style.visibility='visible';
    }
    function hideLegend() {
        var elem = document.getElementById('legend');
        elem.style.visibility='hidden';
        elem.innerHTML = "";
    }
    // -->
    </script>

  </body>
</html>